Monitoring Functions in Azure
Don't let your business down! Make sure to monitor all your Azure Functions and gain access to details without the Azure portal.
This page provides documentation about the Azure Function Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the Functions. You can manage the monitoring thresholds for the Function; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Function page.
Example list of monitored Functions in a Nodinite Monitor View
Monitoring Features
- State Evaluation - Provide state evaluation according to pre-defined policy.
If Nodinite can't check your Function items' state, chances are no one else can use them either.
- Application Insight<s have Automatic Discovery
- The Nodinite Azure Agent makes use of the Azure Rest API. Hence, Functions presents automatically.
- Category-based monitoring - The monitored Resources groups by the Nodinite concept of Categories.
- Share access to individual items from within Nodinite using one or more role-based Monitor Views.
State evaluation for Functions
The Functions to monitor manifests within Nodinite as one or more Resources. For example, if you have three Functions, you will have three Resources in Nodinite.
- The Nodinite Resources name is the same as the deployed Function name.
- Monitored Functions belong to 'Function' Category:
Many other Azure related Categories exists as well, please review the Azure Monitoring Overview
- The Application name is created with the following pattern:
Configuration name/Resource Group Name
Each item (presented in Nodinite as a Resource) evaluates with a state (i.e. OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources.
Function
For Function Resources, the state evaluates as described in the table below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Error threshold is breached | Function is about to expire, or is expired | Edit | |
| Warning | Warning threshold is breached | Function is about to expire, or is expired | Edit | |
| OK | Within user-defined thresholds | Details |
Alert history for Function
During root cause analysis or other purposes, it might be useful to understand how often your Function problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span either for all your Function or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected Function item |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.